bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 2 Apr 2019 09:57:08 +0000 (10:57 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 2 Apr 2019 09:57:08 +0000 (10:57 +0100)
commit1b4039943d723febde7771cdcceacbf844374035
tree099f05d23e03dc2ec90ec5b7f08d460980431a15
parent736be0729b9c1a5d4f1bac22f42b14b559bb6ffc
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h